Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856555e3479c4abff3cd2c7554b7b8707f1fc2b5310fda49eeb56fd72b43a69b

Tx prefix hash: ab8831a260f514a37ca19210ef2f8a08c82565ea7512fb50eabe91a8f0a19e9a
Tx public key: 73cd3468aa9ce1a3ad71482ccdfbbc244ce8ab152d273d4294f8df853334fc13
Timestamp: 1736246244 Timestamp [UCT]: 2025-01-07 10:37:24 Age [y:d:h:m:s]: 00:296:13:43:16
Block: 1192106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209464 RingCT/type: yes/0
Extra: 0173cd3468aa9ce1a3ad71482ccdfbbc244ce8ab152d273d4294f8df853334fc1302110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 238b0585d19841fde60e7acaa8ddfb84d11dc1866eb3b50a9ec9dc90824ceea4 0.600000000000 1678653 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": 1192116, "vin": [ { "gen": { "height": 1192106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "238b0585d19841fde60e7acaa8ddfb84d11dc1866eb3b50a9ec9dc90824ceea4" } } ], "extra": [ 1, 115, 205, 52, 104, 170, 156, 225, 163, 173, 113, 72, 44, 205, 251, 188, 36, 76, 232, 171, 21, 45, 39, 61, 66, 148, 248, 223, 133, 51, 52, 252, 19, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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