Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd523900c4f8038f9319ea84e160d37db1f667e6fc284b746a7b649462e22828

Tx prefix hash: 4eaa702680518a1fa2636bd8ad96247f14e42cfd0b482de34a57b92a801225bd
Tx public key: 3cc526691a6e40faecb66bc1dd65dfcbb2f4e1488d3ed580990cc6232d327dfc
Timestamp: 1717832271 Timestamp [UCT]: 2024-06-08 07:37:51 Age [y:d:h:m:s]: 01:007:00:44:30
Block: 1039589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265825 RingCT/type: yes/0
Extra: 013cc526691a6e40faecb66bc1dd65dfcbb2f4e1488d3ed580990cc6232d327dfc02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc128bcb503c32619a41a55a3ad523e097d5f2a9b079f675ea20ed04ff9f7dbc 0.600000000000 1508232 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": 1039599, "vin": [ { "gen": { "height": 1039589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc128bcb503c32619a41a55a3ad523e097d5f2a9b079f675ea20ed04ff9f7dbc" } } ], "extra": [ 1, 60, 197, 38, 105, 26, 110, 64, 250, 236, 182, 107, 193, 221, 101, 223, 203, 178, 244, 225, 72, 141, 62, 213, 128, 153, 12, 198, 35, 45, 50, 125, 252, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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