Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2af0412d1dd8536089d85f3d09ec0268d862e54c51c72d2baed2d1be04e5f8f

Tx prefix hash: 9afefa57057f998a82d97e7a80ba6426ada70b3fea01099409b5def5bf38474d
Tx public key: 106147223cc29c5a6e382be10d8e1f506d95a63a74288182a50ffba018ce72fd
Timestamp: 1710190110 Timestamp [UCT]: 2024-03-11 20:48:30 Age [y:d:h:m:s]: 00:348:10:32:11
Block: 976235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249100 RingCT/type: yes/0
Extra: 01106147223cc29c5a6e382be10d8e1f506d95a63a74288182a50ffba018ce72fd0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0f749de30f11bdfe842e4fa0cb945a78a0f3882b83bf5adffaf76dc532f98cf 0.600000000000 1436226 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": 976245, "vin": [ { "gen": { "height": 976235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0f749de30f11bdfe842e4fa0cb945a78a0f3882b83bf5adffaf76dc532f98cf" } } ], "extra": [ 1, 16, 97, 71, 34, 60, 194, 156, 90, 110, 56, 43, 225, 13, 142, 31, 80, 109, 149, 166, 58, 116, 40, 129, 130, 165, 15, 251, 160, 24, 206, 114, 253, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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