Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd98ee5a7c1ab85f48a8bf6b434f4216ee4d6dc9964fff4a0b950bd9f51421e9

Tx prefix hash: b3b6ab8e46a502a505c59ffe03db65a1e8cf50f32dfacaa4dc36316e5bc6b0c0
Tx public key: 85d1f012b2bfcdc98a9e969df61f4e98ae3162b5126442a28dc0814dfcded89d
Timestamp: 1723493407 Timestamp [UCT]: 2024-08-12 20:10:07 Age [y:d:h:m:s]: 00:247:06:34:27
Block: 1086514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176613 RingCT/type: yes/0
Extra: 0185d1f012b2bfcdc98a9e969df61f4e98ae3162b5126442a28dc0814dfcded89d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c425dc0ec4d924706e1978f6d5e28737b6b46243bfee239bab1af8fe59dae84c 0.600000000000 1561111 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": 1086524, "vin": [ { "gen": { "height": 1086514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c425dc0ec4d924706e1978f6d5e28737b6b46243bfee239bab1af8fe59dae84c" } } ], "extra": [ 1, 133, 209, 240, 18, 178, 191, 205, 201, 138, 158, 150, 157, 246, 31, 78, 152, 174, 49, 98, 181, 18, 100, 66, 162, 141, 192, 129, 77, 252, 222, 216, 157, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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