Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6c5e162a4e31df2711c6209c6dc4c4bd14f6fac123962badabf942a7ce06d78

Tx prefix hash: 74c5c1af964afd14171a8c782b2fa51e5a435daa05023ef8b1c88a2310fecd47
Tx public key: 65cbe124545f44a13aabb1878cc1f9f39d74e5143dda768e904f8be3a8b931ff
Timestamp: 1715121248 Timestamp [UCT]: 2024-05-07 22:34:08 Age [y:d:h:m:s]: 00:331:02:56:12
Block: 1017110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236682 RingCT/type: yes/0
Extra: 0165cbe124545f44a13aabb1878cc1f9f39d74e5143dda768e904f8be3a8b931ff0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e76c7fd75ad9aeebaf98bf50a1e89e2a29a74dd4cc402d4c5516c736d6d98f73 0.600000000000 1480877 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": 1017120, "vin": [ { "gen": { "height": 1017110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e76c7fd75ad9aeebaf98bf50a1e89e2a29a74dd4cc402d4c5516c736d6d98f73" } } ], "extra": [ 1, 101, 203, 225, 36, 84, 95, 68, 161, 58, 171, 177, 135, 140, 193, 249, 243, 157, 116, 229, 20, 61, 218, 118, 142, 144, 79, 139, 227, 168, 185, 49, 255, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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