Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd4ce4a1f81638cde9b7dcd5e5a2c7142de13142858c9f48db60649bf3b135f8

Tx prefix hash: 7e57e1179be6dffc34661798b699d0785ab4485a0f8eeb4d2c9621569198eac8
Tx public key: 3ddaec257e47c1ed9b3d2bb8ecfc9fed6e9e44c0ef7badbb800fc1c9e6ceffad
Timestamp: 1734524704 Timestamp [UCT]: 2024-12-18 12:25:04 Age [y:d:h:m:s]: 00:181:06:47:00
Block: 1177886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129261 RingCT/type: yes/0
Extra: 013ddaec257e47c1ed9b3d2bb8ecfc9fed6e9e44c0ef7badbb800fc1c9e6ceffad0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e9740bd8214bc544ba82b94ed1be78bcef6d01cfb09f7655d1e0ce31e29361 0.600000000000 1664267 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": 1177896, "vin": [ { "gen": { "height": 1177886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e9740bd8214bc544ba82b94ed1be78bcef6d01cfb09f7655d1e0ce31e29361" } } ], "extra": [ 1, 61, 218, 236, 37, 126, 71, 193, 237, 155, 61, 43, 184, 236, 252, 159, 237, 110, 158, 68, 192, 239, 123, 173, 187, 128, 15, 193, 201, 230, 206, 255, 173, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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