Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1cfec3db6df3117f6067f437713a387b4ca47c537a4ef3e7480b2c6c4839b05

Tx prefix hash: 3f6ea7f78ff5d97cd41cdd25d5410a3d7afcc49c678607ad7efad007b2a4c75f
Tx public key: 41e015c9a747983939b6edc84c004de9d41f75c17103476347cd75b1df89a216
Timestamp: 1639400004 Timestamp [UCT]: 2021-12-13 12:53:24 Age [y:d:h:m:s]: 03:092:04:10:01
Block: 394625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844634 RingCT/type: yes/0
Extra: 0141e015c9a747983939b6edc84c004de9d41f75c17103476347cd75b1df89a2160211000000080eb261b4000000000000000000

1 output(s) for total of 30.230401670000 dcy

stealth address amount amount idx
00: 38f85704e011f78ac93c366528af6b0989041d81a06301ece04038562f0d1ba4 30.230401670000 792278 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": 394635, "vin": [ { "gen": { "height": 394625 } } ], "vout": [ { "amount": 30230401670, "target": { "key": "38f85704e011f78ac93c366528af6b0989041d81a06301ece04038562f0d1ba4" } } ], "extra": [ 1, 65, 224, 21, 201, 167, 71, 152, 57, 57, 182, 237, 200, 76, 0, 77, 233, 212, 31, 117, 193, 113, 3, 71, 99, 71, 205, 117, 177, 223, 137, 162, 22, 2, 17, 0, 0, 0, 8, 14, 178, 97, 180, 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