Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bd6f60189def257489bbfcdac00f47a7b9a2c7423239aa320cb44f02d17ad34

Tx prefix hash: 7e8c68d4b038cec9da5d624d2a8ad1b50c2cf18831c11bccc4ff373841d023f7
Tx public key: 3edfdc6c3ea4d82734abf1e642ffebee171a18cff4c34be410dd0c882ac82688
Timestamp: 1743242662 Timestamp [UCT]: 2025-03-29 10:04:22 Age [y:d:h:m:s]: 00:243:20:24:20
Block: 1249762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172027 RingCT/type: yes/0
Extra: 013edfdc6c3ea4d82734abf1e642ffebee171a18cff4c34be410dd0c882ac826880211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c673c6996144cc603138bbb6c8a68371f532a6704421dff1b3dbde58711a2cd 0.600000000000 1736803 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": 1249772, "vin": [ { "gen": { "height": 1249762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c673c6996144cc603138bbb6c8a68371f532a6704421dff1b3dbde58711a2cd" } } ], "extra": [ 1, 62, 223, 220, 108, 62, 164, 216, 39, 52, 171, 241, 230, 66, 255, 235, 238, 23, 26, 24, 207, 244, 195, 75, 228, 16, 221, 12, 136, 42, 200, 38, 136, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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