Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6398a66f613e18b03b56ed013e65ad7c90d4bafc1a86806bbbccde1c8af8ff43

Tx prefix hash: 81755dccf544179e85abca322ff2ef7a3650b4b2b9e7e2d51fb9d0ce130e102e
Tx public key: 6420816a9e569d1f857c8ecafc4a5e01e764a188ea3b0714515eeaa83ad43971
Timestamp: 1702011712 Timestamp [UCT]: 2023-12-08 05:01:52 Age [y:d:h:m:s]: 01:122:14:19:31
Block: 908419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348761 RingCT/type: yes/0
Extra: 016420816a9e569d1f857c8ecafc4a5e01e764a188ea3b0714515eeaa83ad43971021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07c6461a16bb1c59ed8a101338bbac3633d9604f7e7ae5aa640c1aa5d3302132 0.600000000000 1365452 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": 908429, "vin": [ { "gen": { "height": 908419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07c6461a16bb1c59ed8a101338bbac3633d9604f7e7ae5aa640c1aa5d3302132" } } ], "extra": [ 1, 100, 32, 129, 106, 158, 86, 157, 31, 133, 124, 142, 202, 252, 74, 94, 1, 231, 100, 161, 136, 234, 59, 7, 20, 81, 94, 234, 168, 58, 212, 57, 113, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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