Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d718142ad9080fc7ead44c5db7aeb083110e4fe2fe23d8b7e2887ca1cce0c081

Tx prefix hash: de07b0fe08d23b5f570559fbb5948be7aefc6ab2fc227e91c98a6e67e08b000d
Tx public key: 06ddef5b063b92e61ebc6a96ffd7e90126bc31f98df0f7318279d619be9f7be4
Timestamp: 1722066393 Timestamp [UCT]: 2024-07-27 07:46:33 Age [y:d:h:m:s]: 00:232:14:46:55
Block: 1074684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166167 RingCT/type: yes/0
Extra: 0106ddef5b063b92e61ebc6a96ffd7e90126bc31f98df0f7318279d619be9f7be4021100000020e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4adcbf96f6b1d6af08cdc77ef749e2381f0b30977ede784f5b841141d77025cb 0.600000000000 1547201 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": 1074694, "vin": [ { "gen": { "height": 1074684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4adcbf96f6b1d6af08cdc77ef749e2381f0b30977ede784f5b841141d77025cb" } } ], "extra": [ 1, 6, 221, 239, 91, 6, 59, 146, 230, 30, 188, 106, 150, 255, 215, 233, 1, 38, 188, 49, 249, 141, 240, 247, 49, 130, 121, 214, 25, 190, 159, 123, 228, 2, 17, 0, 0, 0, 32, 233, 20, 221, 21, 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