Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b18104b4a8537f2a141ff7e198a3ab3d2f80bc2d756831483ec9ace52170c0

Tx prefix hash: 2f635aee5ab97f0afe113fbff6fa847ac62961c134bd7e5e341ee90eb11a1b4a
Tx public key: 6c278b2e18a414663b4abe162115a3e386604963513a6b33e2a279d46d0f535e
Timestamp: 1737203094 Timestamp [UCT]: 2025-01-18 12:24:54 Age [y:d:h:m:s]: 00:151:07:44:44
Block: 1200031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107832 RingCT/type: yes/0
Extra: 016c278b2e18a414663b4abe162115a3e386604963513a6b33e2a279d46d0f535e0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fcc0661e0c833e00cbc199a4edc84a06d4481235897413b2e9a05984ad4bfbd 0.600000000000 1686672 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": 1200041, "vin": [ { "gen": { "height": 1200031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fcc0661e0c833e00cbc199a4edc84a06d4481235897413b2e9a05984ad4bfbd" } } ], "extra": [ 1, 108, 39, 139, 46, 24, 164, 20, 102, 59, 74, 190, 22, 33, 21, 163, 227, 134, 96, 73, 99, 81, 58, 107, 51, 226, 162, 121, 212, 109, 15, 83, 94, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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