Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f955ca6e06ddfebe27c4ab8e9e77611edfb9f0001a09b2c32f13d195c3562d3

Tx prefix hash: 1f1d988e9a9296b58092034de71e8b28d5259097269ff830a41ff3ee6d2ad700
Tx public key: b1989e0549b243f2b880c71e2385b936945f11e9e55c239001027d81e6c9e42e
Timestamp: 1743430273 Timestamp [UCT]: 2025-03-31 14:11:13 Age [y:d:h:m:s]: 00:234:07:35:28
Block: 1251311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165200 RingCT/type: yes/0
Extra: 01b1989e0549b243f2b880c71e2385b936945f11e9e55c239001027d81e6c9e42e021100000006def6842b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b892785c1f3fafb55877c83092307f26a2261991d74e4c5808d9e562e7df4b 0.600000000000 1738372 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": 1251321, "vin": [ { "gen": { "height": 1251311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b892785c1f3fafb55877c83092307f26a2261991d74e4c5808d9e562e7df4b" } } ], "extra": [ 1, 177, 152, 158, 5, 73, 178, 67, 242, 184, 128, 199, 30, 35, 133, 185, 54, 148, 95, 17, 233, 229, 92, 35, 144, 1, 2, 125, 129, 230, 201, 228, 46, 2, 17, 0, 0, 0, 6, 222, 246, 132, 43, 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