Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23e4247a28d2474cb36722212b514fb93225f1e0f4d7bf947cf9e06c4cf1a6d7

Tx prefix hash: 64cc68e73467b52ffbda83465a5b9d693a274eb3f7c73424f2be2f5c3927dc37
Tx public key: 8d314d89e4737bdc51a1a82c97bbf4f1366dd748f3ebc8fcd226e44d59e43977
Timestamp: 1708273281 Timestamp [UCT]: 2024-02-18 16:21:21 Age [y:d:h:m:s]: 01:068:02:07:47
Block: 960337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309712 RingCT/type: yes/0
Extra: 018d314d89e4737bdc51a1a82c97bbf4f1366dd748f3ebc8fcd226e44d59e439770211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34799a2ad4aa2c512c33b140f692605dc4aead6114c4aa1a9e855a45135c6ee5 0.600000000000 1419900 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": 960347, "vin": [ { "gen": { "height": 960337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34799a2ad4aa2c512c33b140f692605dc4aead6114c4aa1a9e855a45135c6ee5" } } ], "extra": [ 1, 141, 49, 77, 137, 228, 115, 123, 220, 81, 161, 168, 44, 151, 187, 244, 241, 54, 109, 215, 72, 243, 235, 200, 252, 210, 38, 228, 77, 89, 228, 57, 119, 2, 17, 0, 0, 0, 2, 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