Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f250a1ff6c97372be8392cf0db5bb1df74bbf466844838ca804a0c1a4dbdafe

Tx prefix hash: 3e4f9db6026d44be6fd4682b1004adf9b2290e3dd2ee0f7463dbea45cee25dba
Tx public key: a9694bf3c4059eaa2551118b9f61af3c0823b95364a76b635da489f814741f19
Timestamp: 1727466749 Timestamp [UCT]: 2024-09-27 19:52:29 Age [y:d:h:m:s]: 00:057:15:41:22
Block: 1119464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41190 RingCT/type: yes/0
Extra: 01a9694bf3c4059eaa2551118b9f61af3c0823b95364a76b635da489f814741f1902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b31a3c49fab0fdd3f3aa23e37fd15ac951abf19bd92a62b7f77f1c73f76f1c79 0.600000000000 1601027 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": 1119474, "vin": [ { "gen": { "height": 1119464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b31a3c49fab0fdd3f3aa23e37fd15ac951abf19bd92a62b7f77f1c73f76f1c79" } } ], "extra": [ 1, 169, 105, 75, 243, 196, 5, 158, 170, 37, 81, 17, 139, 159, 97, 175, 60, 8, 35, 185, 83, 100, 167, 107, 99, 93, 164, 137, 248, 20, 116, 31, 25, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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