Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f687f58c30482a3f2af5d0d4ac524746a6862abb3530dc67b07905d85fc94a0

Tx prefix hash: 336f96cbf2a5f1a7c4b900ac420d31f23025353914e4f81fb26e879a4144d464
Tx public key: a399dc4bac9a7881cdb4d147b7d48cab7903b8fe1ed9d6f8b77dfdd169f29e72
Timestamp: 1697273146 Timestamp [UCT]: 2023-10-14 08:45:46 Age [y:d:h:m:s]: 01:165:00:01:33
Block: 869340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378939 RingCT/type: yes/0
Extra: 01a399dc4bac9a7881cdb4d147b7d48cab7903b8fe1ed9d6f8b77dfdd169f29e7202110000000975e3f0e9000000000000000000

1 output(s) for total of 0.808234198000 dcy

stealth address amount amount idx
00: 12ba1a03cfa189fcb091127d8fa6c6981e431e88ce82de15489cb74c9cd7aeac 0.808234198000 1324181 of 0

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": 869350, "vin": [ { "gen": { "height": 869340 } } ], "vout": [ { "amount": 808234198, "target": { "key": "12ba1a03cfa189fcb091127d8fa6c6981e431e88ce82de15489cb74c9cd7aeac" } } ], "extra": [ 1, 163, 153, 220, 75, 172, 154, 120, 129, 205, 180, 209, 71, 183, 212, 140, 171, 121, 3, 184, 254, 30, 217, 214, 248, 183, 125, 253, 209, 105, 242, 158, 114, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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