Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68980a21061717a0a9c80f6ec7d865c169162e1aef7bc93ac0bdcb00739a33a

Tx prefix hash: 548f8a9148dc3792e30d3f0b9cc1c600b1165637b37b04a8f28d600a4e3326b6
Tx public key: b46777c8ce90bc826a5ea5de4458c143ab6f2fb1b8a6a54c750d871364188480
Timestamp: 1715448795 Timestamp [UCT]: 2024-05-11 17:33:15 Age [y:d:h:m:s]: 00:132:20:15:42
Block: 1019853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95131 RingCT/type: yes/0
Extra: 01b46777c8ce90bc826a5ea5de4458c143ab6f2fb1b8a6a54c750d871364188480021100000005679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db1754e785a9ca45f105d534a456bec4af98b827d31254d897733666c513deaf 0.600000000000 1483906 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": 1019863, "vin": [ { "gen": { "height": 1019853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db1754e785a9ca45f105d534a456bec4af98b827d31254d897733666c513deaf" } } ], "extra": [ 1, 180, 103, 119, 200, 206, 144, 188, 130, 106, 94, 165, 222, 68, 88, 193, 67, 171, 111, 47, 177, 184, 166, 165, 76, 117, 13, 135, 19, 100, 24, 132, 128, 2, 17, 0, 0, 0, 5, 103, 154, 138, 129, 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