Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b3f5be9950606cd63813318ae68105ae1cc47baca04883fd6fb8f0539cc2813

Tx prefix hash: 941a2d8cabd81986102fed5196e932b6441a4dea0c0df2347689d38420b0e174
Tx public key: e9a5110de85c999533a111af6541074577dec6d498d87f5fa3e1ab1a346df7c5
Timestamp: 1582909064 Timestamp [UCT]: 2020-02-28 16:57:44 Age [y:d:h:m:s]: 04:252:10:05:02
Block: 73534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073981 RingCT/type: yes/0
Extra: 01e9a5110de85c999533a111af6541074577dec6d498d87f5fa3e1ab1a346df7c50211000000204943cd9f000000000000000000

1 output(s) for total of 350.229022497000 dcy

stealth address amount amount idx
00: e555ae4420d15a8c8e47798963a41c1877a5e0bc91453caddf7114a75fea23a8 350.229022497000 135690 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": 73544, "vin": [ { "gen": { "height": 73534 } } ], "vout": [ { "amount": 350229022497, "target": { "key": "e555ae4420d15a8c8e47798963a41c1877a5e0bc91453caddf7114a75fea23a8" } } ], "extra": [ 1, 233, 165, 17, 13, 232, 92, 153, 149, 51, 161, 17, 175, 101, 65, 7, 69, 119, 222, 198, 212, 152, 216, 127, 95, 163, 225, 171, 26, 52, 109, 247, 197, 2, 17, 0, 0, 0, 32, 73, 67, 205, 159, 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