Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f897c92750597be71464d3b1380b6e19d290ed086ba5e26bdfb98c15a027ee6

Tx prefix hash: 90557b4f28e935fbf036051c342d7c4cdb809b0a99e2daa48b3f84dde6e11ad6
Tx public key: 8e836cdc84a5a0eb6f2cd095cacc5dfa13d13ded6aff9923304ca0258a3bf27f
Timestamp: 1639502986 Timestamp [UCT]: 2021-12-14 17:29:46 Age [y:d:h:m:s]: 03:090:22:07:31
Block: 395486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 843732 RingCT/type: yes/0
Extra: 018e836cdc84a5a0eb6f2cd095cacc5dfa13d13ded6aff9923304ca0258a3bf27f02110000000dde12510f000000000000000000

1 output(s) for total of 30.032470973000 dcy

stealth address amount amount idx
00: f4380d45d8fdb22f12eedde84a04f8801408041a182a2fd89a9e91e399704020 30.032470973000 793421 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": 395496, "vin": [ { "gen": { "height": 395486 } } ], "vout": [ { "amount": 30032470973, "target": { "key": "f4380d45d8fdb22f12eedde84a04f8801408041a182a2fd89a9e91e399704020" } } ], "extra": [ 1, 142, 131, 108, 220, 132, 165, 160, 235, 111, 44, 208, 149, 202, 204, 93, 250, 19, 209, 61, 237, 106, 255, 153, 35, 48, 76, 160, 37, 138, 59, 242, 127, 2, 17, 0, 0, 0, 13, 222, 18, 81, 15, 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