Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fff191f5a2cf4112b69c6e73d51e2929c63574cff44b8766ffac95eb6bbf7ff

Tx prefix hash: 2f6d3ed44e1ebe6ec2b6eee6dc1b85be3e25d392c2e586de5284adced01e5907
Tx public key: 99fa7ef7275049c8571d6df96abcd07c77b1c6a03f008fefddf3ff212bf937fa
Timestamp: 1695638859 Timestamp [UCT]: 2023-09-25 10:47:39 Age [y:d:h:m:s]: 01:185:21:14:10
Block: 855785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393911 RingCT/type: yes/0
Extra: 0199fa7ef7275049c8571d6df96abcd07c77b1c6a03f008fefddf3ff212bf937fa02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.896249837000 dcy

stealth address amount amount idx
00: d6a97efb09e60142bcd374659c27a1475622d92fa8b30e50dad17fe3044016f8 0.896249837000 1309827 of 0

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": 855795, "vin": [ { "gen": { "height": 855785 } } ], "vout": [ { "amount": 896249837, "target": { "key": "d6a97efb09e60142bcd374659c27a1475622d92fa8b30e50dad17fe3044016f8" } } ], "extra": [ 1, 153, 250, 126, 247, 39, 80, 73, 200, 87, 29, 109, 249, 106, 188, 208, 124, 119, 177, 198, 160, 63, 0, 143, 239, 221, 243, 255, 33, 43, 249, 55, 250, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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