Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c63035d016498d7dbd1b693a77dae04afaaad14e51a9ee671c3d8f6a58f1867

Tx prefix hash: 2b9283fa0130446023fd3aacfcae8d4f1e933a429a5ce9d11ff67e7c6ad0b071
Tx public key: 9630424cee48c2eb8de16682c690195df540b601d4a7649d5ad10b52c31bddd7
Timestamp: 1728316018 Timestamp [UCT]: 2024-10-07 15:46:58 Age [y:d:h:m:s]: 01:030:13:13:18
Block: 1126503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280204 RingCT/type: yes/0
Extra: 019630424cee48c2eb8de16682c690195df540b601d4a7649d5ad10b52c31bddd7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49b59a1a76bf43fdcaeae9c0d3bfac64d33edb8311178c0b3fe6a62edddb4dc3 0.600000000000 1609296 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": 1126513, "vin": [ { "gen": { "height": 1126503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49b59a1a76bf43fdcaeae9c0d3bfac64d33edb8311178c0b3fe6a62edddb4dc3" } } ], "extra": [ 1, 150, 48, 66, 76, 238, 72, 194, 235, 141, 225, 102, 130, 198, 144, 25, 93, 245, 64, 182, 1, 212, 167, 100, 157, 90, 209, 11, 82, 195, 27, 221, 215, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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