Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a2b9be9011d06652be98cb2337985f6e706fbfb08455612a70ee5359a541db

Tx prefix hash: 310e8d860db0470836718dc1aa1c9db1df8f1b13e9e1322d144c5b5abdea3cc9
Tx public key: ac2238e289b3e081a8385bc72b31e81a12a5a63eadc6b7ac62770644abd27b66
Timestamp: 1735737147 Timestamp [UCT]: 2025-01-01 13:12:27 Age [y:d:h:m:s]: 00:169:07:27:45
Block: 1187897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120695 RingCT/type: yes/0
Extra: 01ac2238e289b3e081a8385bc72b31e81a12a5a63eadc6b7ac62770644abd27b66021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2e22b9cf21d97e02b4c6385ac7af5477542ea612fa6485c02631fdad577a67d 0.600000000000 1674394 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": 1187907, "vin": [ { "gen": { "height": 1187897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2e22b9cf21d97e02b4c6385ac7af5477542ea612fa6485c02631fdad577a67d" } } ], "extra": [ 1, 172, 34, 56, 226, 137, 179, 224, 129, 168, 56, 91, 199, 43, 49, 232, 26, 18, 165, 166, 62, 173, 198, 183, 172, 98, 119, 6, 68, 171, 210, 123, 102, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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