Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c942f66a1b011c1260b63b6897c7fd2ab66038692a860a847b36db03216ac446

Tx prefix hash: 6b23af4b2af719cbc33960966a2018bb906daee606f3301acf5caea4e377531a
Tx public key: cbea2b3c265bc0becb362e1daf84de346de14408baaeac0fc77e71a79c7b0f42
Timestamp: 1709289749 Timestamp [UCT]: 2024-03-01 10:42:29 Age [y:d:h:m:s]: 01:112:07:18:32
Block: 968766 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341157 RingCT/type: yes/0
Extra: 01cbea2b3c265bc0becb362e1daf84de346de14408baaeac0fc77e71a79c7b0f420211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d2eb0f321dce9c7c50dc38e8de5ad36bd442256edc949aa80d166800e19252 0.600000000000 1428589 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": 968776, "vin": [ { "gen": { "height": 968766 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d2eb0f321dce9c7c50dc38e8de5ad36bd442256edc949aa80d166800e19252" } } ], "extra": [ 1, 203, 234, 43, 60, 38, 91, 192, 190, 203, 54, 46, 29, 175, 132, 222, 52, 109, 225, 68, 8, 186, 174, 172, 15, 199, 126, 113, 167, 156, 123, 15, 66, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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