Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3778a7c9932c1cf11e66eeb395319dccf7ae9538127e260cf7c7a932233cb786

Tx prefix hash: cdeda7e2fd9443a21919846eec8b1122b5112e92c3016c43c46f89d86ce2ac7c
Tx public key: 6453a3f787b48730802aff2bc5fee0fee832d435d1cf84602f6446443ae9acc9
Timestamp: 1706635015 Timestamp [UCT]: 2024-01-30 17:16:55 Age [y:d:h:m:s]: 01:067:11:12:22
Block: 946733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309287 RingCT/type: yes/0
Extra: 016453a3f787b48730802aff2bc5fee0fee832d435d1cf84602f6446443ae9acc90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2827221144db6d1842e10a6c1ccdf002e5fae91814b82ef12693a7767f0cd0 0.600000000000 1405073 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": 946743, "vin": [ { "gen": { "height": 946733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2827221144db6d1842e10a6c1ccdf002e5fae91814b82ef12693a7767f0cd0" } } ], "extra": [ 1, 100, 83, 163, 247, 135, 180, 135, 48, 128, 42, 255, 43, 197, 254, 224, 254, 232, 50, 212, 53, 209, 207, 132, 96, 47, 100, 70, 68, 58, 233, 172, 201, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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