Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824e733c8a114a3b6cf0d3423e58dd449a6768cd4570fd8043782d11f1fa7748

Tx prefix hash: ebc4a299ca7c921c8ddbbc37851a0df03b9aba4a02ed67c62968d3fa103d32d6
Tx public key: d07e20cdb796b1a7a2889395c2b073ec18b7547ee1b1081329901a8a2266fa1e
Timestamp: 1733868091 Timestamp [UCT]: 2024-12-10 22:01:31 Age [y:d:h:m:s]: 00:101:01:47:10
Block: 1172435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72013 RingCT/type: yes/0
Extra: 01d07e20cdb796b1a7a2889395c2b073ec18b7547ee1b1081329901a8a2266fa1e02110000000a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 600d5b3677f3bdb68467b01d1f351a72024c6586922c762008e6ba6fe4816df8 0.600000000000 1658324 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": 1172445, "vin": [ { "gen": { "height": 1172435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "600d5b3677f3bdb68467b01d1f351a72024c6586922c762008e6ba6fe4816df8" } } ], "extra": [ 1, 208, 126, 32, 205, 183, 150, 177, 167, 162, 136, 147, 149, 194, 176, 115, 236, 24, 183, 84, 126, 225, 177, 8, 19, 41, 144, 26, 138, 34, 102, 250, 30, 2, 17, 0, 0, 0, 10, 31, 10, 83, 235, 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