Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a81d278634aeda1b15677fe0dcac31783aee53449838d287be5d707521bfd1a

Tx prefix hash: 54a82c83bfb959acd6c6781e387bec71ba100d06fed303501248b5312caab917
Tx public key: 84c096c9e98aa24e7c6f9af230af14aa7f715c2b7a44f7a90355fdfd28f967a2
Timestamp: 1732915982 Timestamp [UCT]: 2024-11-29 21:33:02 Age [y:d:h:m:s]: 00:146:02:41:05
Block: 1164535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104256 RingCT/type: yes/0
Extra: 0184c096c9e98aa24e7c6f9af230af14aa7f715c2b7a44f7a90355fdfd28f967a20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c28e04541db3e8937e8ee20c421cecf5d8afad24a67afccbdf554ea40a617359 0.600000000000 1650208 of 15

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": 1164545, "vin": [ { "gen": { "height": 1164535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c28e04541db3e8937e8ee20c421cecf5d8afad24a67afccbdf554ea40a617359" } } ], "extra": [ 1, 132, 192, 150, 201, 233, 138, 162, 78, 124, 111, 154, 242, 48, 175, 20, 170, 127, 113, 92, 43, 122, 68, 247, 169, 3, 85, 253, 253, 40, 249, 103, 162, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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