Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64868129338faa26fa41402f07c61cf3afb272d6a84e01f8e696cd19e00c62f

Tx prefix hash: ed6b1e96378bdfadf24e1c0db2136cb711d697cea9fc3c511ae56773c104e3c2
Tx public key: 3d74f1cf1b2cbc0edb666be1fe05d640e98a652b4b39b1838c580d448e38930b
Timestamp: 1737172635 Timestamp [UCT]: 2025-01-18 03:57:15 Age [y:d:h:m:s]: 00:153:21:42:10
Block: 1199767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109660 RingCT/type: yes/0
Extra: 013d74f1cf1b2cbc0edb666be1fe05d640e98a652b4b39b1838c580d448e38930b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f228f44b99e052e325d739fbb92ece2ab52fb0d7e78350b3991bb9ff9eeaa8b 0.600000000000 1686400 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": 1199777, "vin": [ { "gen": { "height": 1199767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f228f44b99e052e325d739fbb92ece2ab52fb0d7e78350b3991bb9ff9eeaa8b" } } ], "extra": [ 1, 61, 116, 241, 207, 27, 44, 188, 14, 219, 102, 107, 225, 254, 5, 214, 64, 233, 138, 101, 43, 75, 57, 177, 131, 140, 88, 13, 68, 142, 56, 147, 11, 2, 17, 0, 0, 0, 1, 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