Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7bba1699c0e4679f6930108f8f9fd30ea8e549acd16c05fe1a1eff7b6b174b2

Tx prefix hash: 533dcd90e42285b56b3cb6f76972a5930325ec92cdd8796f4dc7231457bed9b5
Tx public key: 5b08ecaced97af0c186246f6125ca0636c779f4cee6cf67b5ec4879893e9f555
Timestamp: 1711460554 Timestamp [UCT]: 2024-03-26 13:42:34 Age [y:d:h:m:s]: 00:335:11:58:18
Block: 986784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239819 RingCT/type: yes/0
Extra: 015b08ecaced97af0c186246f6125ca0636c779f4cee6cf67b5ec4879893e9f55502110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7bb302051ac1ad2d2f73eef4dc91e7b25612af222ceea9c8a43c8a1d9e4d436 0.600000000000 1447019 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": 986794, "vin": [ { "gen": { "height": 986784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7bb302051ac1ad2d2f73eef4dc91e7b25612af222ceea9c8a43c8a1d9e4d436" } } ], "extra": [ 1, 91, 8, 236, 172, 237, 151, 175, 12, 24, 98, 70, 246, 18, 92, 160, 99, 108, 119, 159, 76, 238, 108, 246, 123, 94, 196, 135, 152, 147, 233, 245, 85, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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