Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c1c1ea151e4500bfea78890bc4ae02d6c167040379a42243d59ed41e596fe94

Tx prefix hash: 285b80646439cd0cbdd7458fe4fed685e7578efce7aee3949e4efe1e6f16f37b
Tx public key: 027868b854da0a7c9bf73a573f23e4e6367a6f47e38025b797b3416a831f4284
Timestamp: 1728456229 Timestamp [UCT]: 2024-10-09 06:43:49 Age [y:d:h:m:s]: 00:156:02:50:50
Block: 1127661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111375 RingCT/type: yes/0
Extra: 01027868b854da0a7c9bf73a573f23e4e6367a6f47e38025b797b3416a831f428402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6be347796db8008fd8bfb2b3b9bb48180df14ce7a9d05d589e81a5066643e0 0.600000000000 1610468 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": 1127671, "vin": [ { "gen": { "height": 1127661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6be347796db8008fd8bfb2b3b9bb48180df14ce7a9d05d589e81a5066643e0" } } ], "extra": [ 1, 2, 120, 104, 184, 84, 218, 10, 124, 155, 247, 58, 87, 63, 35, 228, 230, 54, 122, 111, 71, 227, 128, 37, 183, 151, 179, 65, 106, 131, 31, 66, 132, 2, 17, 0, 0, 0, 4, 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