Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b887ede4e50c0fe2e48eb2e1f81329a1055f42312eeb8cd9fcde77ff58a75262

Tx prefix hash: e6de995cc95cf6af5bcbc7a4d5d0323a5f6853c32a7c1283c2ac8efa76df78d4
Tx public key: 466873534f9d70018ed23abeb902d8f28c916dfad7b0cca603eb3daa9944f2da
Timestamp: 1588567170 Timestamp [UCT]: 2020-05-04 04:39:30 Age [y:d:h:m:s]: 04:196:23:08:33
Block: 98419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1056291 RingCT/type: yes/0
Extra: 01466873534f9d70018ed23abeb902d8f28c916dfad7b0cca603eb3daa9944f2da02110000001ed81c26c0000000000000000000

1 output(s) for total of 289.666159643000 dcy

stealth address amount amount idx
00: 536618be1429b5dc6a3d76128e97ebdc937c35b5070f51d786a4b03e12d30669 289.666159643000 173924 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": 98429, "vin": [ { "gen": { "height": 98419 } } ], "vout": [ { "amount": 289666159643, "target": { "key": "536618be1429b5dc6a3d76128e97ebdc937c35b5070f51d786a4b03e12d30669" } } ], "extra": [ 1, 70, 104, 115, 83, 79, 157, 112, 1, 142, 210, 58, 190, 185, 2, 216, 242, 140, 145, 109, 250, 215, 176, 204, 166, 3, 235, 61, 170, 153, 68, 242, 218, 2, 17, 0, 0, 0, 30, 216, 28, 38, 192, 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