Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dae1a35ca2f298218f247f91673edf63027702e49a70dd11e6d183027a761e0

Tx prefix hash: 826284956bbe2dbe8795fa805012e5b59e301e29e69c17ebb264f68e52c73ba2
Tx public key: 1cc0dd5a50059255f7a8bf1b3bac3a94f7f2f2a7a84343f94242a9e78c57436a
Timestamp: 1764316005 Timestamp [UCT]: 2025-11-28 07:46:45 Age [y:d:h:m:s]: 00:025:12:58:27
Block: 1421822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18286 RingCT/type: yes/0
Extra: 011cc0dd5a50059255f7a8bf1b3bac3a94f7f2f2a7a84343f94242a9e78c57436a0211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3d4b01ef871b4464bc18977add531658209cdbf4205e3e87d8f5fc46a88d37a 0.600000000000 1910383 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": 1421832, "vin": [ { "gen": { "height": 1421822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3d4b01ef871b4464bc18977add531658209cdbf4205e3e87d8f5fc46a88d37a" } } ], "extra": [ 1, 28, 192, 221, 90, 80, 5, 146, 85, 247, 168, 191, 27, 59, 172, 58, 148, 247, 242, 242, 167, 168, 67, 67, 249, 66, 66, 169, 231, 140, 87, 67, 106, 2, 17, 0, 0, 0, 1, 78, 123, 252, 9, 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