Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068b3bc8d8c8eae94a23263709a6c0b0a687a2bb649f125d62baf856c1910aaf

Tx prefix hash: c6918ce471a4a4081d43c375a1f3f28209d951c095da592e18b4ec318ff0284b
Tx public key: a4e5f172638076857df88e6c5bfc0391cec0cf245a40206f9bb59a485a49ed2f
Timestamp: 1723477103 Timestamp [UCT]: 2024-08-12 15:38:23 Age [y:d:h:m:s]: 01:093:18:37:56
Block: 1086380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325500 RingCT/type: yes/0
Extra: 01a4e5f172638076857df88e6c5bfc0391cec0cf245a40206f9bb59a485a49ed2f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ffe6ff7deb3ec0b08645ecfa4ea70848360c81db92f5c9cabd332a70d371c7d 0.600000000000 1560977 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": 1086390, "vin": [ { "gen": { "height": 1086380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ffe6ff7deb3ec0b08645ecfa4ea70848360c81db92f5c9cabd332a70d371c7d" } } ], "extra": [ 1, 164, 229, 241, 114, 99, 128, 118, 133, 125, 248, 142, 108, 91, 252, 3, 145, 206, 192, 207, 36, 90, 64, 32, 111, 155, 181, 154, 72, 90, 73, 237, 47, 2, 17, 0, 0, 0, 5, 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