Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31760f5fc988916414e8d3e2ea93d16dbf44a78f9f2741786add5acea790e43

Tx prefix hash: 1bf040f52f0d5773858e59da26c16f71dc3623f82c467713f282bc3b87577cc8
Tx public key: ece826466f4392089a42ea2c6e34d6b67dae2531dc39804f769648ad2c7dafc7
Timestamp: 1726686788 Timestamp [UCT]: 2024-09-18 19:13:08 Age [y:d:h:m:s]: 00:196:08:22:48
Block: 1112991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140140 RingCT/type: yes/0
Extra: 01ece826466f4392089a42ea2c6e34d6b67dae2531dc39804f769648ad2c7dafc702110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35c906d1b1e4a9ec73b31e2aa3f933fc247be0ced6001d6e89cfcff694b6c69c 0.600000000000 1592506 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": 1113001, "vin": [ { "gen": { "height": 1112991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35c906d1b1e4a9ec73b31e2aa3f933fc247be0ced6001d6e89cfcff694b6c69c" } } ], "extra": [ 1, 236, 232, 38, 70, 111, 67, 146, 8, 154, 66, 234, 44, 110, 52, 214, 182, 125, 174, 37, 49, 220, 57, 128, 79, 118, 150, 72, 173, 44, 125, 175, 199, 2, 17, 0, 0, 0, 5, 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