Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f63fad5648ce8b8d5e199d69d94d55bcc15f6a0424c6c44cca7385f81be0b44

Tx prefix hash: 1ac95624d4d4ce0279dce15b1b4d63f28f572ce7dd6bc7a33bdf78dfb52d3d28
Tx public key: 88a3e8070040463005062d93dbdf69a213e511aef36aab4ad89fe0bcb2fb3812
Timestamp: 1673445481 Timestamp [UCT]: 2023-01-11 13:58:01 Age [y:d:h:m:s]: 02:102:10:18:49
Block: 672463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594880 RingCT/type: yes/0
Extra: 0188a3e8070040463005062d93dbdf69a213e511aef36aab4ad89fe0bcb2fb38120211000000018b7b6602000000000000000000

1 output(s) for total of 3.629534108000 dcy

stealth address amount amount idx
00: 59f0dd501183b47b28c673f3029c05b769c3aef258ee890719929a2b865bec24 3.629534108000 1114014 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": 672473, "vin": [ { "gen": { "height": 672463 } } ], "vout": [ { "amount": 3629534108, "target": { "key": "59f0dd501183b47b28c673f3029c05b769c3aef258ee890719929a2b865bec24" } } ], "extra": [ 1, 136, 163, 232, 7, 0, 64, 70, 48, 5, 6, 45, 147, 219, 223, 105, 162, 19, 229, 17, 174, 243, 106, 171, 74, 216, 159, 224, 188, 178, 251, 56, 18, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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