Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd21345febe5124f4b9b6dc813448c6876a937a3933e2fab067c5b914c4e9df3

Tx prefix hash: 7d56f0c4839c0b86b34f2b1d9e93a80e483e49504cff59e2cbcf2f613ac7a6e2
Tx public key: ec34320ba8df237cb90bca357a3353716276da1579f26fc8374b5e3644317579
Timestamp: 1706142808 Timestamp [UCT]: 2024-01-25 00:33:28 Age [y:d:h:m:s]: 01:301:05:51:44
Block: 942645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474112 RingCT/type: yes/0
Extra: 01ec34320ba8df237cb90bca357a3353716276da1579f26fc8374b5e36443175790211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e243e613236b62712ef79a35a639f566946533310ed2c329e6cc8e3bb782926a 0.600000000000 1400821 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": 942655, "vin": [ { "gen": { "height": 942645 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e243e613236b62712ef79a35a639f566946533310ed2c329e6cc8e3bb782926a" } } ], "extra": [ 1, 236, 52, 50, 11, 168, 223, 35, 124, 185, 11, 202, 53, 122, 51, 83, 113, 98, 118, 218, 21, 121, 242, 111, 200, 55, 75, 94, 54, 68, 49, 117, 121, 2, 17, 0, 0, 0, 2, 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