Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415d513a3916a231bcd55781bb4a78fa78d9c3606fd3ec7ecaf036607001b795

Tx prefix hash: b927ea16c593a4f39dc9432e35c0c3a3cfbc93e159c6678858593c1019ed5ea3
Tx public key: 47a5a9dccc25f409f91403199ca6c6cf404dfcb7682c2d6665819886768226f4
Timestamp: 1714474972 Timestamp [UCT]: 2024-04-30 11:02:52 Age [y:d:h:m:s]: 00:335:13:00:17
Block: 1011744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239870 RingCT/type: yes/0
Extra: 0147a5a9dccc25f409f91403199ca6c6cf404dfcb7682c2d6665819886768226f40211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09fb464d1b8e48507d2f4c590dd8cf90ece01bc62e24c3f21e57cafe8a48a0c0 0.600000000000 1474056 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": 1011754, "vin": [ { "gen": { "height": 1011744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09fb464d1b8e48507d2f4c590dd8cf90ece01bc62e24c3f21e57cafe8a48a0c0" } } ], "extra": [ 1, 71, 165, 169, 220, 204, 37, 244, 9, 249, 20, 3, 25, 156, 166, 198, 207, 64, 77, 252, 183, 104, 44, 45, 102, 101, 129, 152, 134, 118, 130, 38, 244, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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