Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 551f4699787028e0fbc900d51757017cb31ca1cbe4dc3ca512cb3d6e610032be

Tx prefix hash: 691c7b7ec3d0085e3d15df6c6e04d2161d4054758bc79f720f338a9a3bcc7d80
Tx public key: 03edba1172158956b2c25dc7ee870a30f98fd9a2b413b8c0433361046de885d0
Timestamp: 1715234635 Timestamp [UCT]: 2024-05-09 06:03:55 Age [y:d:h:m:s]: 00:324:09:31:53
Block: 1018054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231867 RingCT/type: yes/0
Extra: 0103edba1172158956b2c25dc7ee870a30f98fd9a2b413b8c0433361046de885d00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61859f0ab0250f80f90e43f9e836062793f708f2ba7120e158fbaa499c534f28 0.600000000000 1481839 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": 1018064, "vin": [ { "gen": { "height": 1018054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61859f0ab0250f80f90e43f9e836062793f708f2ba7120e158fbaa499c534f28" } } ], "extra": [ 1, 3, 237, 186, 17, 114, 21, 137, 86, 178, 194, 93, 199, 238, 135, 10, 48, 249, 143, 217, 162, 180, 19, 184, 192, 67, 51, 97, 4, 109, 232, 133, 208, 2, 17, 0, 0, 0, 1, 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