Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f230c1a5657c952b825cdb09049817b49b6bbcfbb54b49cbb138b487e6f5de79

Tx prefix hash: 86e525777d4f8aac55672fa40ced8dab879f7337aebc570b8ae312a16bf4b9e5
Tx public key: b10d519b658d764323a6c8d20d7ece5f529f6b6f5a4d187150b388c295bd8311
Timestamp: 1705397090 Timestamp [UCT]: 2024-01-16 09:24:50 Age [y:d:h:m:s]: 01:084:14:04:27
Block: 936476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321546 RingCT/type: yes/0
Extra: 01b10d519b658d764323a6c8d20d7ece5f529f6b6f5a4d187150b388c295bd83110211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3b1d9ca0a7289bd81c71c801e5452016bfcd269c1e5959b15a93617e1c7dcc 0.600000000000 1394504 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": 936486, "vin": [ { "gen": { "height": 936476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3b1d9ca0a7289bd81c71c801e5452016bfcd269c1e5959b15a93617e1c7dcc" } } ], "extra": [ 1, 177, 13, 81, 155, 101, 141, 118, 67, 35, 166, 200, 210, 13, 126, 206, 95, 82, 159, 107, 111, 90, 77, 24, 113, 80, 179, 136, 194, 149, 189, 131, 17, 2, 17, 0, 0, 0, 8, 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