Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b66b03e6d68f6aeb999dab5ca71d6f1c4dd36b250134c749caa692b980d819b6

Tx prefix hash: ba32837bd19e145eb735365f0c7ff70093320317eb037b6fec1a802b782e9781
Tx public key: 6cd4f37c397daddc2e3b70451bb47c7fe24ff41ad0fa0b0c76cfd2f7f259a59d
Timestamp: 1739320638 Timestamp [UCT]: 2025-02-12 00:37:18 Age [y:d:h:m:s]: 00:282:23:25:44
Block: 1217300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199995 RingCT/type: yes/0
Extra: 016cd4f37c397daddc2e3b70451bb47c7fe24ff41ad0fa0b0c76cfd2f7f259a59d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5df25213297034b12622d4cc30ddc171759300f79e2101811b9935e85a15f4 0.600000000000 1704109 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": 1217310, "vin": [ { "gen": { "height": 1217300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5df25213297034b12622d4cc30ddc171759300f79e2101811b9935e85a15f4" } } ], "extra": [ 1, 108, 212, 243, 124, 57, 125, 173, 220, 46, 59, 112, 69, 27, 180, 124, 127, 226, 79, 244, 26, 208, 250, 11, 12, 118, 207, 210, 247, 242, 89, 165, 157, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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