Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3006cf8dc249a3ee83a66a4f08593ea75a18474c8522c016d1b4d328caf3b297

Tx prefix hash: 3f65ec7b95e4b7071e9bbb542e653b987a44fea046912bd9a8bba70668eb9d2d
Tx public key: affb3019c5a31d55fb3716c02e7500cfaddea1c477986d0092ecf41c34aa94e4
Timestamp: 1738652028 Timestamp [UCT]: 2025-02-04 06:53:48 Age [y:d:h:m:s]: 00:290:17:28:12
Block: 1211754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205553 RingCT/type: yes/0
Extra: 01affb3019c5a31d55fb3716c02e7500cfaddea1c477986d0092ecf41c34aa94e4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f60f253ef9062d02e6d917eae69852a2e54044843a20d1a0ca6fc3465ac4f7ad 0.600000000000 1698517 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": 1211764, "vin": [ { "gen": { "height": 1211754 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f60f253ef9062d02e6d917eae69852a2e54044843a20d1a0ca6fc3465ac4f7ad" } } ], "extra": [ 1, 175, 251, 48, 25, 197, 163, 29, 85, 251, 55, 22, 192, 46, 117, 0, 207, 173, 222, 161, 196, 119, 152, 109, 0, 146, 236, 244, 28, 52, 170, 148, 228, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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