Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 36f045ab25086bc9a23461759a9bbeb30177937ab73861de1b6e9cb392463946

Tx prefix hash: 7b47317c16863089f4fb11a6cc926f06f6c8dcb0e52fa97096a5cc4f8abfd183
Tx public key: dcfc40b64ce8e418354c27b6ddf06d241b5d611924af99ed3b16ba27ba2c3198
Timestamp: 1714890225 Timestamp [UCT]: 2024-05-05 06:23:45 Age [y:d:h:m:s]: 00:260:14:21:29
Block: 1015213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186451 RingCT/type: yes/0
Extra: 01dcfc40b64ce8e418354c27b6ddf06d241b5d611924af99ed3b16ba27ba2c319802110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a5c2d040f3a89ec39899720a952d1f804e01c3d3fd8ce0a28ae20729fe17d34 0.600000000000 1478512 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1015223, "vin": [ { "gen": { "height": 1015213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a5c2d040f3a89ec39899720a952d1f804e01c3d3fd8ce0a28ae20729fe17d34" } } ], "extra": [ 1, 220, 252, 64, 182, 76, 232, 228, 24, 53, 76, 39, 182, 221, 240, 109, 36, 27, 93, 97, 25, 36, 175, 153, 237, 59, 22, 186, 39, 186, 44, 49, 152, 2, 17, 0, 0, 0, 13, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8