Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9df5b8ec3fdc198ad82e3cbf69353ea47a79484997412d426f55e3dd6601385c

Tx prefix hash: d3873868da26d1da6885e021aea2e0d570c6311dbfd565df6077075e7c38b4dd
Tx public key: 6083f7e7a6765a64a1e869bca74c8d5720115b4ca6aee97d50e3b356abd846a4
Timestamp: 1718742510 Timestamp [UCT]: 2024-06-18 20:28:30 Age [y:d:h:m:s]: 00:337:00:48:13
Block: 1047130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240891 RingCT/type: yes/0
Extra: 016083f7e7a6765a64a1e869bca74c8d5720115b4ca6aee97d50e3b356abd846a402110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61db07f5962207d843edfff420141ec6072815845e14ef9104ea3e0679bc0137 0.600000000000 1516949 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": 1047140, "vin": [ { "gen": { "height": 1047130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61db07f5962207d843edfff420141ec6072815845e14ef9104ea3e0679bc0137" } } ], "extra": [ 1, 96, 131, 247, 231, 166, 118, 90, 100, 161, 232, 105, 188, 167, 76, 141, 87, 32, 17, 91, 76, 166, 174, 233, 125, 80, 227, 179, 86, 171, 216, 70, 164, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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