Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f697487e3b9d6685dcc02c8c0f207cea31ef7ced46293d1a3b83c72cac15a30

Tx prefix hash: b120a1cf5694f225897fcd4357d4fe8b0f279b0491e666879d02c9bb6cd654a1
Tx public key: a18fa22a1790cccfa85cb445a45282557aa41c31e445eac982c0f42dfacdfa6d
Timestamp: 1711851580 Timestamp [UCT]: 2024-03-31 02:19:40 Age [y:d:h:m:s]: 01:040:03:57:34
Block: 990013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289675 RingCT/type: yes/0
Extra: 01a18fa22a1790cccfa85cb445a45282557aa41c31e445eac982c0f42dfacdfa6d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a830162d0ae90cebca73757cfb694ef856f7b49902885513fa16f0be89e328 0.600000000000 1450333 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": 990023, "vin": [ { "gen": { "height": 990013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a830162d0ae90cebca73757cfb694ef856f7b49902885513fa16f0be89e328" } } ], "extra": [ 1, 161, 143, 162, 42, 23, 144, 204, 207, 168, 92, 180, 69, 164, 82, 130, 85, 122, 164, 28, 49, 228, 69, 234, 201, 130, 192, 244, 45, 250, 205, 250, 109, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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