Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 526c6b21635238dfcd5db8eeead33dcf0a12b054901b486cfbdf87971a86024c

Tx prefix hash: 82dab03311efd5c1960918594f1b89e76bd02a623b9dbec5deb26b1927d5ffc8
Tx public key: 0f8b7cd2e0cee0e184f1b30fd25bf163f8bcb94379bcfc0a81704065f341af18
Timestamp: 1736400268 Timestamp [UCT]: 2025-01-09 05:24:28 Age [y:d:h:m:s]: 00:070:22:12:52
Block: 1193387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50480 RingCT/type: yes/0
Extra: 010f8b7cd2e0cee0e184f1b30fd25bf163f8bcb94379bcfc0a81704065f341af180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71649a21db6040da85d28b1a8ecee6777a76e2c96d651cad7770b0a38c2a0aaf 0.600000000000 1679946 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": 1193397, "vin": [ { "gen": { "height": 1193387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71649a21db6040da85d28b1a8ecee6777a76e2c96d651cad7770b0a38c2a0aaf" } } ], "extra": [ 1, 15, 139, 124, 210, 224, 206, 224, 225, 132, 241, 179, 15, 210, 91, 241, 99, 248, 188, 185, 67, 121, 188, 252, 10, 129, 112, 64, 101, 243, 65, 175, 24, 2, 17, 0, 0, 0, 3, 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