Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af82c3dfe5e4b58e775a9149ec6a2515c578e43fd4f397b5880971c094b347c6

Tx prefix hash: e7e812bb174b988df6cf489e2f8ad161501ac74f9129a840879a5f01f4becd80
Tx public key: 90254b6e99adb52ec57025a674f01235765b9b11d8c06c115f64c9a0cadf2668
Timestamp: 1766264447 Timestamp [UCT]: 2025-12-20 21:00:47 Age [y:d:h:m:s]: 00:000:23:50:00
Block: 1437981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695 RingCT/type: yes/0
Extra: 0190254b6e99adb52ec57025a674f01235765b9b11d8c06c115f64c9a0cadf26680211000000037b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7a0ecf9c72b14ba612c4a63b016e254964d8d926ef9bbc9ee0ff54606c49d4 0.600000000000 1926796 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": 1437991, "vin": [ { "gen": { "height": 1437981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7a0ecf9c72b14ba612c4a63b016e254964d8d926ef9bbc9ee0ff54606c49d4" } } ], "extra": [ 1, 144, 37, 75, 110, 153, 173, 181, 46, 197, 112, 37, 166, 116, 240, 18, 53, 118, 91, 155, 17, 216, 192, 108, 17, 95, 100, 201, 160, 202, 223, 38, 104, 2, 17, 0, 0, 0, 3, 123, 30, 81, 172, 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