Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5527c1a44e7683847d89d3feb0c31cd296d19ac3b2e0418866a555c6b460031a

Tx prefix hash: 91714d8bae596a3a6b4e6257383914896570c19df1780a8fbbb8e0ab56e55696
Tx public key: c765b4bda33ae59c25a86626aa44a22c3b7d862694f4a978f8e6e04cc9b526f6
Timestamp: 1727710621 Timestamp [UCT]: 2024-09-30 15:37:01 Age [y:d:h:m:s]: 00:054:16:13:42
Block: 1121484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39065 RingCT/type: yes/0
Extra: 01c765b4bda33ae59c25a86626aa44a22c3b7d862694f4a978f8e6e04cc9b526f6021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6b1784fc85191b36e17b3f4952f3c472c48aa16416e2a5136c7e0b73ea7d1c2 0.600000000000 1603765 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": 1121494, "vin": [ { "gen": { "height": 1121484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6b1784fc85191b36e17b3f4952f3c472c48aa16416e2a5136c7e0b73ea7d1c2" } } ], "extra": [ 1, 199, 101, 180, 189, 163, 58, 229, 156, 37, 168, 102, 38, 170, 68, 162, 44, 59, 125, 134, 38, 148, 244, 169, 120, 248, 230, 224, 76, 201, 181, 38, 246, 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