Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90fa3fb2e13996168f63873a981910431d2f9306ea2c444f2a45060c9487a08a

Tx prefix hash: 708ffca7aafb626788ad5c9667de4462ae6533f99d8d83596970a316e17cd21b
Tx public key: 2edc49c5e7e265754bb3b6d20a80492d193cf47f574c7202a955b9a3e9e40bf3
Timestamp: 1764940917 Timestamp [UCT]: 2025-12-05 13:21:57 Age [y:d:h:m:s]: 00:058:00:54:35
Block: 1427012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41371 RingCT/type: yes/0
Extra: 012edc49c5e7e265754bb3b6d20a80492d193cf47f574c7202a955b9a3e9e40bf302110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7b78e66f3cbdec1a1b359f14ea0bf339c71df99e02bb81ef0e053e5e95cc55e 0.600000000000 1915711 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": 1427022, "vin": [ { "gen": { "height": 1427012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7b78e66f3cbdec1a1b359f14ea0bf339c71df99e02bb81ef0e053e5e95cc55e" } } ], "extra": [ 1, 46, 220, 73, 197, 231, 226, 101, 117, 75, 179, 182, 210, 10, 128, 73, 45, 25, 60, 244, 127, 87, 76, 114, 2, 169, 85, 185, 163, 233, 228, 11, 243, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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