Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 538bba9347e8dc6c84029338949c056143eb31ff879d831ee8183099efae6d7a

Tx prefix hash: 47ecc4ed421fd0b6403f3dc8505d2ecb9afac0a7d2e5cb440593f5c7e2a950d3
Tx public key: 653395c1a684521ae7d49db3f2bb5a58c5ab90f31108632024778b09c14125d9
Timestamp: 1733341600 Timestamp [UCT]: 2024-12-04 19:46:40 Age [y:d:h:m:s]: 00:107:16:31:45
Block: 1168062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76763 RingCT/type: yes/0
Extra: 01653395c1a684521ae7d49db3f2bb5a58c5ab90f31108632024778b09c14125d90211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 081f42157584ef186c2d459b5d63eb290e7b89b188cf798d3a26f4dd72286d59 0.600000000000 1653769 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": 1168072, "vin": [ { "gen": { "height": 1168062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "081f42157584ef186c2d459b5d63eb290e7b89b188cf798d3a26f4dd72286d59" } } ], "extra": [ 1, 101, 51, 149, 193, 166, 132, 82, 26, 231, 212, 157, 179, 242, 187, 90, 88, 197, 171, 144, 243, 17, 8, 99, 32, 36, 119, 139, 9, 193, 65, 37, 217, 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