Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be9b703e936509d11379f95a380b0f63d6871c354b9f6552aa669ee243c41fb6

Tx prefix hash: fc08c774d06d8ef160a22fcb448b936a27b461c4aee900e616ebda3127026167
Tx public key: 54d50d57bd418416a9b41f6e34c6808cd259fd66c8aa63bb87c66d59b9260f48
Timestamp: 1733778620 Timestamp [UCT]: 2024-12-09 21:10:20 Age [y:d:h:m:s]: 00:113:05:54:59
Block: 1171691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80707 RingCT/type: yes/0
Extra: 0154d50d57bd418416a9b41f6e34c6808cd259fd66c8aa63bb87c66d59b9260f48021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a5ee4e57e02a84d9e110372d6eb275be85135e691e2a3713dfa61d8b28a7e89 0.600000000000 1657480 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": 1171701, "vin": [ { "gen": { "height": 1171691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a5ee4e57e02a84d9e110372d6eb275be85135e691e2a3713dfa61d8b28a7e89" } } ], "extra": [ 1, 84, 213, 13, 87, 189, 65, 132, 22, 169, 180, 31, 110, 52, 198, 128, 140, 210, 89, 253, 102, 200, 170, 99, 187, 135, 198, 109, 89, 185, 38, 15, 72, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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