Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7b176d3b8871c2faa07366ae9b85271075dea10e2721ca9f882ff7570d1f7e

Tx prefix hash: 0b78539530475f526d2a089c7f7f9778c8af24ae89585c173f2c9d8e05dbde47
Tx public key: 34cf3b53eb624836ea5dc9365514b94e208fbd343f6bd8daf2185cd81266bac9
Timestamp: 1706931108 Timestamp [UCT]: 2024-02-03 03:31:48 Age [y:d:h:m:s]: 00:347:20:17:15
Block: 949189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249029 RingCT/type: yes/0
Extra: 0134cf3b53eb624836ea5dc9365514b94e208fbd343f6bd8daf2185cd81266bac902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c38260d70114b95efc85f5f52fd2eee46d41fde84ae6067bf5a2886c4e73c089 0.600000000000 1407711 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": 949199, "vin": [ { "gen": { "height": 949189 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c38260d70114b95efc85f5f52fd2eee46d41fde84ae6067bf5a2886c4e73c089" } } ], "extra": [ 1, 52, 207, 59, 83, 235, 98, 72, 54, 234, 93, 201, 54, 85, 20, 185, 78, 32, 143, 189, 52, 63, 107, 216, 218, 242, 24, 92, 216, 18, 102, 186, 201, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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