Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8d566201bb648df07f61f7acadfea790330041c7823ec36469e579d0f1a39db

Tx prefix hash: 65a98caaa1ce81632a6c03185fdd21951c1787934af24b7f1d79f8b01aef3901
Tx public key: 6bd66b68c0b92b7e6a7302a40b975db7bae22a2a2d0b90a1407a5e5939149622
Timestamp: 1708627008 Timestamp [UCT]: 2024-02-22 18:36:48 Age [y:d:h:m:s]: 01:049:13:24:08
Block: 963267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296450 RingCT/type: yes/0
Extra: 016bd66b68c0b92b7e6a7302a40b975db7bae22a2a2d0b90a1407a5e59391496220211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907ef967e9b3d13fc74bc7a80283c483d26b909ce26b4879279445bd5f2cc047 0.600000000000 1422968 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": 963277, "vin": [ { "gen": { "height": 963267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907ef967e9b3d13fc74bc7a80283c483d26b909ce26b4879279445bd5f2cc047" } } ], "extra": [ 1, 107, 214, 107, 104, 192, 185, 43, 126, 106, 115, 2, 164, 11, 151, 93, 183, 186, 226, 42, 42, 45, 11, 144, 161, 64, 122, 94, 89, 57, 20, 150, 34, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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