Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd34081c5d8fdc70693e8e8e82d4b93e0ef30cd1bfc88353dfd4a769ed3a7267

Tx prefix hash: a849a0db9ef5421e4471da4a7f83f86a9e8e2f1382b3c22c337d85ac788b8e2c
Tx public key: 03e3fc9e25d1726874aca8f77458f99453c11d9fd63d37f1b03055576cce05d1
Timestamp: 1738162205 Timestamp [UCT]: 2025-01-29 14:50:05 Age [y:d:h:m:s]: 00:321:19:24:50
Block: 1207707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227794 RingCT/type: yes/0
Extra: 0103e3fc9e25d1726874aca8f77458f99453c11d9fd63d37f1b03055576cce05d1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 673ea2857ddcbec1513ea933e48337adbb28b3b1bed1b0f9b409aeba21239c82 0.600000000000 1694432 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": 1207717, "vin": [ { "gen": { "height": 1207707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "673ea2857ddcbec1513ea933e48337adbb28b3b1bed1b0f9b409aeba21239c82" } } ], "extra": [ 1, 3, 227, 252, 158, 37, 209, 114, 104, 116, 172, 168, 247, 116, 88, 249, 148, 83, 193, 29, 159, 214, 61, 55, 241, 176, 48, 85, 87, 108, 206, 5, 209, 2, 17, 0, 0, 0, 1, 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