Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2839577b9ec5cd08a18baf611be38028eb33a6e079dee8055cf3ff2c7596f1f

Tx prefix hash: d81a3ff42af79c5dddfbb20ef8e04fa3b27d0986e7cabb6403c54dcc2aa2ec23
Tx public key: f9d727e7d405d57812c6b90f493e04c15444f2483ecff5dcde5de68a89f27c7b
Timestamp: 1745348979 Timestamp [UCT]: 2025-04-22 19:09:39 Age [y:d:h:m:s]: 00:259:16:40:42
Block: 1267195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183396 RingCT/type: yes/0
Extra: 01f9d727e7d405d57812c6b90f493e04c15444f2483ecff5dcde5de68a89f27c7b02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c02d73ef4dcaa183d97dfe248dbe4e86eb656d203b910015a69330e053161096 0.600000000000 1754422 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": 1267205, "vin": [ { "gen": { "height": 1267195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c02d73ef4dcaa183d97dfe248dbe4e86eb656d203b910015a69330e053161096" } } ], "extra": [ 1, 249, 215, 39, 231, 212, 5, 213, 120, 18, 198, 185, 15, 73, 62, 4, 193, 84, 68, 242, 72, 62, 207, 245, 220, 222, 93, 230, 138, 137, 242, 124, 123, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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