Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1128aea9e4e61f56322e0dddb71507af49f16607791d5f48bcfe8a263f123278

Tx prefix hash: 12b4f4a3431a3e38b77f964194738680d2894c7a4f283df43bb034dce3421808
Tx public key: 844f728bdbf3965c8ca963d57e1f489b82bd229670bf0b08c36404c57c6aa57a
Timestamp: 1752122842 Timestamp [UCT]: 2025-07-10 04:47:22 Age [y:d:h:m:s]: 00:204:06:29:37
Block: 1322397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144463 RingCT/type: yes/0
Extra: 01844f728bdbf3965c8ca963d57e1f489b82bd229670bf0b08c36404c57c6aa57a02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6ceaf9169b08e2a7f53f871b861256fb48defd58b1763d78e362ff9b05ae947 0.600000000000 1810126 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": 1322407, "vin": [ { "gen": { "height": 1322397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6ceaf9169b08e2a7f53f871b861256fb48defd58b1763d78e362ff9b05ae947" } } ], "extra": [ 1, 132, 79, 114, 139, 219, 243, 150, 92, 140, 169, 99, 213, 126, 31, 72, 155, 130, 189, 34, 150, 112, 191, 11, 8, 195, 100, 4, 197, 124, 106, 165, 122, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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