Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df8a3be8108a0ae6cc82e6e1455793d8ad9e2d938d298bb594bf507517aa26d7

Tx prefix hash: c9b4af8ff4bd39e2b25d0adfd951c119d2e26226386202597cd12e3426ba17e2
Tx public key: 1f38fe81f85fef155d59392b79ea9f42237f8b7f7c8ab036bb5bdf4d425e2960
Timestamp: 1699375905 Timestamp [UCT]: 2023-11-07 16:51:45 Age [y:d:h:m:s]: 01:179:17:42:34
Block: 886575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389661 RingCT/type: yes/0
Extra: 011f38fe81f85fef155d59392b79ea9f42237f8b7f7c8ab036bb5bdf4d425e2960021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.708612801000 dcy

stealth address amount amount idx
00: b502cf1ca6d4daea7562e55c08279166b5117db87c6bd2f61304bdf062753926 0.708612801000 1342402 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": 886585, "vin": [ { "gen": { "height": 886575 } } ], "vout": [ { "amount": 708612801, "target": { "key": "b502cf1ca6d4daea7562e55c08279166b5117db87c6bd2f61304bdf062753926" } } ], "extra": [ 1, 31, 56, 254, 129, 248, 95, 239, 21, 93, 89, 57, 43, 121, 234, 159, 66, 35, 127, 139, 127, 124, 138, 176, 54, 187, 91, 223, 77, 66, 94, 41, 96, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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