Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169c5172fc41ab4b93a185d353d47b6cede72f347f58d7e1dfa9e4beaa74f997

Tx prefix hash: afaa3aca187045e758cd949ad65ebec9bd661fad5670383db3f4b97946d16f23
Tx public key: 7e8d725dfd0a40a69924b5af3ba8d211804d1350de986ac4f5ced6fa71f1e864
Timestamp: 1744396660 Timestamp [UCT]: 2025-04-11 18:37:40 Age [y:d:h:m:s]: 00:221:19:36:32
Block: 1259312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156259 RingCT/type: yes/0
Extra: 017e8d725dfd0a40a69924b5af3ba8d211804d1350de986ac4f5ced6fa71f1e864021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5cd04a68837dd32f65dc073987e429e331879ec0f0fd3f1b274e4e48c10a6d90 0.600000000000 1746451 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": 1259322, "vin": [ { "gen": { "height": 1259312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5cd04a68837dd32f65dc073987e429e331879ec0f0fd3f1b274e4e48c10a6d90" } } ], "extra": [ 1, 126, 141, 114, 93, 253, 10, 64, 166, 153, 36, 181, 175, 59, 168, 210, 17, 128, 77, 19, 80, 222, 152, 106, 196, 245, 206, 214, 250, 113, 241, 232, 100, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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