Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67eeec948f70f3cbdebc19d3a0dc61f2bf79fe4c88373de0a3c43ab33b4c2cb8

Tx prefix hash: b3639442e31591d852c907a06608c3337d1a27358a37f2638d3da823f818bd0d
Tx public key: a3c5f1e44f4865f86dc855d1ca02ab32e1f0208ba6e4067ceb52145c74d942b0
Timestamp: 1728004505 Timestamp [UCT]: 2024-10-04 01:15:05 Age [y:d:h:m:s]: 00:179:09:11:37
Block: 1123920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127990 RingCT/type: yes/0
Extra: 01a3c5f1e44f4865f86dc855d1ca02ab32e1f0208ba6e4067ceb52145c74d942b002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f81fcc2ffe5ff80a4b2ee59b3a561e3c07f3c892c1aba5f0ee3f00795f705a43 0.600000000000 1606469 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": 1123930, "vin": [ { "gen": { "height": 1123920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f81fcc2ffe5ff80a4b2ee59b3a561e3c07f3c892c1aba5f0ee3f00795f705a43" } } ], "extra": [ 1, 163, 197, 241, 228, 79, 72, 101, 248, 109, 200, 85, 209, 202, 2, 171, 50, 225, 240, 32, 139, 166, 228, 6, 124, 235, 82, 20, 92, 116, 217, 66, 176, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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