Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79d225e4c9e6d84f00ba078504e4fbb6fc34ce4e2ada5082c99676992785ea95

Tx prefix hash: 0d683ac6a82f4722d4f85b50f4cb5f4d7f730d5da333d53b86ff0e958f7fa17d
Tx public key: d023aa3c55e5b6cc6fe46ff742e4aabd49fb274a840efba6b4c63e143d75c0aa
Timestamp: 1760517502 Timestamp [UCT]: 2025-10-15 08:38:22 Age [y:d:h:m:s]: 00:043:21:17:01
Block: 1390355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31417 RingCT/type: yes/0
Extra: 01d023aa3c55e5b6cc6fe46ff742e4aabd49fb274a840efba6b4c63e143d75c0aa021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5680443bf92a370241bb1ab6cbe4e0d3ef0dc1f6f0ae70224883f798aa4caedc 0.600000000000 1878596 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": 1390365, "vin": [ { "gen": { "height": 1390355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5680443bf92a370241bb1ab6cbe4e0d3ef0dc1f6f0ae70224883f798aa4caedc" } } ], "extra": [ 1, 208, 35, 170, 60, 85, 229, 182, 204, 111, 228, 111, 247, 66, 228, 170, 189, 73, 251, 39, 74, 132, 14, 251, 166, 180, 198, 62, 20, 61, 117, 192, 170, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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