Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d809c98bba511a65e9c630c98a0fe1e0a01a267cad0cf644188484fd33c847d

Tx prefix hash: 4c28efc9e05ea2f95e0c258623b800bd07b24ca9d739b432dbe761f16b94a4cc
Tx public key: a5d0abdf09fca885336910c8071d7e98ddc68cf80ee4cef9438ff04a0f108f2f
Timestamp: 1701023910 Timestamp [UCT]: 2023-11-26 18:38:30 Age [y:d:h:m:s]: 01:344:10:13:05
Block: 900224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505044 RingCT/type: yes/0
Extra: 01a5d0abdf09fca885336910c8071d7e98ddc68cf80ee4cef9438ff04a0f108f2f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.638534211000 dcy

stealth address amount amount idx
00: 39f92b8ae7aa6700809b3526d6e1aaa1c60f82a59b9d712ed2834eef227271e6 0.638534211000 1356711 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": 900234, "vin": [ { "gen": { "height": 900224 } } ], "vout": [ { "amount": 638534211, "target": { "key": "39f92b8ae7aa6700809b3526d6e1aaa1c60f82a59b9d712ed2834eef227271e6" } } ], "extra": [ 1, 165, 208, 171, 223, 9, 252, 168, 133, 51, 105, 16, 200, 7, 29, 126, 152, 221, 198, 140, 248, 14, 228, 206, 249, 67, 143, 240, 74, 15, 16, 143, 47, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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