Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85326e85485e9b3b6e7b91193e61362c1d91b3240b7793f89e2fea6001334b80

Tx prefix hash: 611cf9158ba4ce75a62039bf43be5677365d2335d48a86b7be5f409c1e9f61cd
Tx public key: 0e3d0320763b05381113a9899f420f27777357aadab2dfd74daa70f15ace57a9
Timestamp: 1701749755 Timestamp [UCT]: 2023-12-05 04:15:55 Age [y:d:h:m:s]: 01:110:07:58:14
Block: 906240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340006 RingCT/type: yes/0
Extra: 010e3d0320763b05381113a9899f420f27777357aadab2dfd74daa70f15ace57a9021100000003e08532b6000000000000000000

1 output(s) for total of 0.609888797000 dcy

stealth address amount amount idx
00: 43ef6df641e9b714dcf6cc7a8f0d6dd9e3d70e6bc84ae1ec68fa1f44122945eb 0.609888797000 1363167 of 0

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": 906250, "vin": [ { "gen": { "height": 906240 } } ], "vout": [ { "amount": 609888797, "target": { "key": "43ef6df641e9b714dcf6cc7a8f0d6dd9e3d70e6bc84ae1ec68fa1f44122945eb" } } ], "extra": [ 1, 14, 61, 3, 32, 118, 59, 5, 56, 17, 19, 169, 137, 159, 66, 15, 39, 119, 115, 87, 170, 218, 178, 223, 215, 77, 170, 112, 241, 90, 206, 87, 169, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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