Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95a1f915fe5f81a1ca9b878515b52811473427d5ac572014e6412a9cd4c60a0b

Tx prefix hash: 0e5edfd1d17435ab7398600fb7e137da8ad7cda74f9190431ec62027f85238dc
Tx public key: 4af3bb67b0af377fa7505a421e4c1ecc906c016096ecf2ee8b5488553b90bbaa
Timestamp: 1719327628 Timestamp [UCT]: 2024-06-25 15:00:28 Age [y:d:h:m:s]: 00:323:07:55:18
Block: 1051968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231086 RingCT/type: yes/0
Extra: 014af3bb67b0af377fa7505a421e4c1ecc906c016096ecf2ee8b5488553b90bbaa0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b030df7105b0d6a2f9b2d1e25889ac811ffd81b819e42ea0aeaaf67cdf771f4 0.600000000000 1522289 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": 1051978, "vin": [ { "gen": { "height": 1051968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b030df7105b0d6a2f9b2d1e25889ac811ffd81b819e42ea0aeaaf67cdf771f4" } } ], "extra": [ 1, 74, 243, 187, 103, 176, 175, 55, 127, 167, 80, 90, 66, 30, 76, 30, 204, 144, 108, 1, 96, 150, 236, 242, 238, 139, 84, 136, 85, 59, 144, 187, 170, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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