Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a80ef9d0c7701c01186e894d3ee12462c806e0f74f02ed41ed7cb2e502844d87

Tx prefix hash: 183e791e7b9d6cce710a9141d1edaba84ae01ed886edb57080f6c5ec76cf4a0d
Tx public key: 653498a5e7f7d10f787eed3c0fe72b00055841430ddee41c93358f3eff1f0210
Timestamp: 1719670535 Timestamp [UCT]: 2024-06-29 14:15:35 Age [y:d:h:m:s]: 00:341:14:06:23
Block: 1054825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244125 RingCT/type: yes/0
Extra: 01653498a5e7f7d10f787eed3c0fe72b00055841430ddee41c93358f3eff1f02100211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77e8edd291c8e8c16ca2b15d94e7c2a7e44ba074daaafd2ed2ad0aa840dba41b 0.600000000000 1525216 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": 1054835, "vin": [ { "gen": { "height": 1054825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77e8edd291c8e8c16ca2b15d94e7c2a7e44ba074daaafd2ed2ad0aa840dba41b" } } ], "extra": [ 1, 101, 52, 152, 165, 231, 247, 209, 15, 120, 126, 237, 60, 15, 231, 43, 0, 5, 88, 65, 67, 13, 222, 228, 28, 147, 53, 143, 62, 255, 31, 2, 16, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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