Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fc87fd7fcaf0a44d8c2cc47247004500fb8dfddcdcccb9e481b9669673a7d7a

Tx prefix hash: d508317368ecf42aa9a45e22b7de1a109cdc4feebeca5cf792567b2d45431235
Tx public key: 5b20973d1e0f9ca1b01687fed7952dc7e5680fcab5118821564849dc93a7bd72
Timestamp: 1590650244 Timestamp [UCT]: 2020-05-28 07:17:24 Age [y:d:h:m:s]: 04:249:05:30:39
Block: 103740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105337 RingCT/type: yes/0
Extra: 015b20973d1e0f9ca1b01687fed7952dc7e5680fcab5118821564849dc93a7bd720211000003926ef253e7000000000000000000

1 output(s) for total of 278.142319926000 dcy

stealth address amount amount idx
00: 4ff6188df84d576034b59bed02ad7fd2a748c798bba1cf2a9a7f505af826d221 278.142319926000 181977 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": 103750, "vin": [ { "gen": { "height": 103740 } } ], "vout": [ { "amount": 278142319926, "target": { "key": "4ff6188df84d576034b59bed02ad7fd2a748c798bba1cf2a9a7f505af826d221" } } ], "extra": [ 1, 91, 32, 151, 61, 30, 15, 156, 161, 176, 22, 135, 254, 215, 149, 45, 199, 229, 104, 15, 202, 181, 17, 136, 33, 86, 72, 73, 220, 147, 167, 189, 114, 2, 17, 0, 0, 3, 146, 110, 242, 83, 231, 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