Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab37f9168d29451fcd02cbcf6ce3ac22492a33e1a77838e50cf60b6ea05d79d5

Tx prefix hash: 00addbf35f95a5844d0eb39f28bb425c6365a2a4360ba759bb85aa13f025a58d
Tx public key: f851e70616371dbe0db8876d46c5bfd2bc5da04a5babe86a582a4007838b8542
Timestamp: 1708713648 Timestamp [UCT]: 2024-02-23 18:40:48 Age [y:d:h:m:s]: 00:338:11:49:18
Block: 963987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242069 RingCT/type: yes/0
Extra: 01f851e70616371dbe0db8876d46c5bfd2bc5da04a5babe86a582a4007838b854202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6310477d0c2ab7d55c6a66f26e21cac756cf59b4e2364b02e6edc9f878ebc03 0.600000000000 1423714 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": 963997, "vin": [ { "gen": { "height": 963987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6310477d0c2ab7d55c6a66f26e21cac756cf59b4e2364b02e6edc9f878ebc03" } } ], "extra": [ 1, 248, 81, 231, 6, 22, 55, 29, 190, 13, 184, 135, 109, 70, 197, 191, 210, 188, 93, 160, 74, 91, 171, 232, 106, 88, 42, 64, 7, 131, 139, 133, 66, 2, 17, 0, 0, 0, 2, 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