Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4428c18dbf89829867d72fe8c61d737322d57acccaef3425b8a1ec3e53e7338e

Tx prefix hash: 9bed3e3f4b722cf8ef7e8b15ed25f5130503f6a41747d866db5b366a3b5f06d1
Tx public key: c76c35f108086ea54c1ca4c76d5f9b6b9efeacc7424333e86cca5124a6368ceb
Timestamp: 1733465504 Timestamp [UCT]: 2024-12-06 06:11:44 Age [y:d:h:m:s]: 00:158:09:28:24
Block: 1169090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113023 RingCT/type: yes/0
Extra: 01c76c35f108086ea54c1ca4c76d5f9b6b9efeacc7424333e86cca5124a6368ceb0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6ca453590d7468b8a72b66543ba825c575ae0902cbc3e25cc3784d0a33fdfca 0.600000000000 1654803 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": 1169100, "vin": [ { "gen": { "height": 1169090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6ca453590d7468b8a72b66543ba825c575ae0902cbc3e25cc3784d0a33fdfca" } } ], "extra": [ 1, 199, 108, 53, 241, 8, 8, 110, 165, 76, 28, 164, 199, 109, 95, 155, 107, 158, 254, 172, 199, 66, 67, 51, 232, 108, 202, 81, 36, 166, 54, 140, 235, 2, 17, 0, 0, 0, 2, 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