Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379e986d201ce2d928c9cd1069d33aa233949793a59deea31ae54bb5ff2eba84

Tx prefix hash: 4b62683d70e9b74c763f9b54428af60039a670a6ffc830aefe6629ddd76c5fb7
Tx public key: 31c9b8c764c695aa54ab781a382029bb82656b340bb802271d6503a603547de5
Timestamp: 1589363599 Timestamp [UCT]: 2020-05-13 09:53:19 Age [y:d:h:m:s]: 04:230:09:24:04
Block: 100483 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1084726 RingCT/type: yes/0
Extra: 0131c9b8c764c695aa54ab781a382029bb82656b340bb802271d6503a603547de502110000043360e3cc90000000000000000000

1 output(s) for total of 285.140475647000 dcy

stealth address amount amount idx
00: aae89c6455c266dd9a3da8b973192890246221d0fb1cd1b26acd0f0dca291313 285.140475647000 177027 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": 100493, "vin": [ { "gen": { "height": 100483 } } ], "vout": [ { "amount": 285140475647, "target": { "key": "aae89c6455c266dd9a3da8b973192890246221d0fb1cd1b26acd0f0dca291313" } } ], "extra": [ 1, 49, 201, 184, 199, 100, 198, 149, 170, 84, 171, 120, 26, 56, 32, 41, 187, 130, 101, 107, 52, 11, 184, 2, 39, 29, 101, 3, 166, 3, 84, 125, 229, 2, 17, 0, 0, 4, 51, 96, 227, 204, 144, 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