Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f217ce029a91827a49ed607cf0e9720374a616a18152397dd37c4816864e0f0

Tx prefix hash: c202d3eb97d24355ab25bd75a3fccc0b9157aca8bc976fac1133fc05a7dfb269
Tx public key: c25ab8bee9c03fe5ac2503e9a50ccc8b5fc848498710f2aee9a2a5a6087f25b1
Timestamp: 1584093138 Timestamp [UCT]: 2020-03-13 09:52:18 Age [y:d:h:m:s]: 04:357:02:10:55
Block: 81907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150035 RingCT/type: yes/0
Extra: 01c25ab8bee9c03fe5ac2503e9a50ccc8b5fc848498710f2aee9a2a5a6087f25b1021100000014995a6b02000000000000000000

1 output(s) for total of 328.555615966000 dcy

stealth address amount amount idx
00: 05ebd3298159bcc612ef0e8495ff42ddaa9ff14c4a9617ed6a1854462cf9179a 328.555615966000 149533 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": 81917, "vin": [ { "gen": { "height": 81907 } } ], "vout": [ { "amount": 328555615966, "target": { "key": "05ebd3298159bcc612ef0e8495ff42ddaa9ff14c4a9617ed6a1854462cf9179a" } } ], "extra": [ 1, 194, 90, 184, 190, 233, 192, 63, 229, 172, 37, 3, 233, 165, 12, 204, 139, 95, 200, 72, 73, 135, 16, 242, 174, 233, 162, 165, 166, 8, 127, 37, 177, 2, 17, 0, 0, 0, 20, 153, 90, 107, 2, 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